Objectives
6 users tested the prototypes of Taskly:
- 3 users tested the non-interactive prototype on paper. They had to simulate their behavior by pointing the items they would click or interact with.
- Following to these 3 tests, improvements were made based on the results. An interactive prototype was then created based on wireframes made with UXPin. The prototype was built using InvisionApp to enhance the simulation of using a device.
3 different users then tested the interactive prototype. A new set of improvements were made based on what the results taught me. Each user tested the app on a different device: desktop, tablet and mobile.
3 different users then tested the interactive prototype. A new set of improvements were made based on what the results taught me. Each user tested the app on a different device: desktop, tablet and mobile.
Script
Before starting the test, a brief explanation was given to the user on:
- What is Taskly.
- If the user did not correspond to one of the personas, what types of users are expected to use it.
- What is the goal of the test. Emphasis was put on the fact that the app was tested to improve it, not the actual user.
- The list of tasks to perform.
Tasks
- On the Login page, the user logs in to Taskly with their user credentials.
- On the dashboard, the user clicks the button “New project”.
- A modal window appears with inviting the user to choose a title. The user inserts a title in the input and clicks the “Create” button.
- The project is created and appears with an empty list of task. The user clicks the button “Create a task”.
- A modal window appears inviting the user to choose a title and a sprint. The sprint is pre-selected to “Sprint 1”. The user inserts a title in the input and clicks the “Create” button.
- The task is created and appears with all the fields being empty. If on mobile/tablet, the user selects the Files tab.
- The user clicks the button “Upload a file”.
- The user uploads a file from their device.
- The file is uploaded onto Taskly. The page shows the preview of the file.
Learnings
Positives
- Users were able to perform all the actions without needing help on all the versions of the app - desktop, tablet and mobile.
- The menu was easy to identify.
- Most icons in the navigation were easy to understand. Menu items had behaviours that were close to the users’ expectations.
- The buttons to use in order to create items (Projects, Tasks, Files) were easy to identify and to spot in the layout thanks to the prominent “+” icon.
- Apart from a few exceptions, these actions could be performed very quickly, without hesitation.
- The feedback from the interview at the end of the session was positive.
Issues
In the main navigation, the notification icon (a light bulb) was not easy to understand. 2 out of 3 users were confused of its meaning. They were also wondering whether the light bulb would be on or off and what would it mean for the project or for the app.Solution applied: The notification icon got replaced with a bell.
When creating a task, the mention of “Sprint” was confusing. Users seemed to block on it before clicking “Create”. They were not sure if the default option “Sprint 1” was correct.
Solution applied: Sprints are now turned off by default for a new project. It is possible to turn on Sprints in the Project Settings.
Solution applied: Sprints are now turned off by default for a new project. It is possible to turn on Sprints in the Project Settings.
On the mobile version, one user had some difficulties when having to add a team member to a project. It can be done by clicking the “Settings” icon on the right side of the project name.
Solution applied: On the mobile app, the top bar is exactly the same throughout the screens. This allows consistency although it can make some parts of the app crowded with icons. On improvement that could be done would be to have a different content for the top bar according to the content. On a project, the top bar would contain the name and icon of the project with the settings icons. This could help the user finding out options such as adding a new team member.
Solution applied: On the mobile app, the top bar is exactly the same throughout the screens. This allows consistency although it can make some parts of the app crowded with icons. On improvement that could be done would be to have a different content for the top bar according to the content. On a project, the top bar would contain the name and icon of the project with the settings icons. This could help the user finding out options such as adding a new team member.
